-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace lib:/// scheme by mvn:/// and file:/// and jar+file:/// everywhere #1969
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ion and configuration process by adding a messages field to PathConfig
… errors that PathConfig creation detects
tests to run
|
``` rascal>resolveLocation(|std:///|) loc: |jar+file:///Users/jurgenv/git/rascal/target/rascal-0.40.3-RC2-SNAPSHOT.jar!/org/rascalmpl/library/| ```
This PR fixes #1961 |
…hile testing from rascal/target/classes instead of from a jar file. now the tests can succeed as well
DavyLandman
reviewed
Feb 6, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small comments.
…wn class to avoid cyclic static block dependencies
…the stdlib resolver by removing a call to mavenize. tricky business.
…ad projects from a common workspace folder, to be able to deal with the typepal source dependency of the rascal project
…rs to read projects from a common workspace folder, to be able to deal with the typepal source dependency of the rascal project" This reverts commit 7c77df9.
…endency cycle is introduced, and fixed a number of minor issues
…ndency to typepal to a version that has rascal itself provided to avoid loading an older vallang via that route
… This can happen in case of diamond dependencies of open Rascal projects in the IDE
DavyLandman
approved these changes
Feb 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
lib:///
scheme. This also removes a lot of printing on stderr.mvn:///
schememessages
, including version clashes on the rascal and rascal-lsp project, missing pom.xml files, etc.These were the TODO's:
mvn:///groupid!artifactid!version
lib:///
in the processing of dependencies (Require-Libraries) with other schemes, includingmvn
,file
, andjar+file
. This means sometimes dynamically computing an absolute path rather than leaving it to an opaque scheme.lib:///
scheme that is now introduced by thePackager
. Some form of relocation is necessary, but it can't be the oldlib:///
scheme anymore.This fixes #1916, #1961, #1826, #1825, #1824, #1777, #1767, and #1478
Downstream projects like rascal-lsp and rascal-maven-plugin may need some modifications:
URIUtil.correctLocation("lib", name)
should becomePathConfig.resolveDependencyFromResourcesOnCurrentClasspath("name")
orURIUtil.correctLocation("mvn", etc.)